Systems and methods for generating status requests for units of work

ABSTRACT

Systems and methods for generating status requests for units of work are disclosed. Some implementations may: manage environment state information maintaining a collaboration environment; identify one or more work unit records having potentially incorrect status values for a status parameter; generate status requests prompting user input to update the potentially incorrect status values for the one or more work unit records identified; and effectuate presentation of the status requests, such that the first status request is presented via a client computing platform associated with the first user.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods for generatingstatus requests for units of work.

BACKGROUND

Collaboration environments enable users to assign projects, tasks, orother assignments to assignees to complete. Such collaborationenvironments enable users to work in a more organized and efficientmanner. However, upon completion, users often forget to update theprojects and/or tasks to indicate they are complete. As such, projectand/or task supervisors and managers are left in the dark and unaware ofthe true status of the project and/or task.

SUMMARY

In typical online collaboration environments for managing workflow,project/team leaders often have to follow-up and/or checked off whenindividual tasks are completed because assignees often forget to do so.Generating status requests for units of work as described herein helpprevent project/team leaders from having to follow-up with individualassignees. Instead, units of work that might need status updates areidentified and status requests prompting updates from users aregenerated and presented to the users. In some implementations, users maybe incentivized to provide user input responding to status requests viaincentive offers.

One aspect of the present disclosure relates to a system configured forgenerating status requests for units of work. The system may include oneor more hardware processors configured by machine-readable instructions.The processor(s) may be configured to manage environment stateinformation maintaining a collaboration environment. The environmentstate information may include values of user parameters and values ofwork unit parameters. The values of the user parameters may be organizedin user records corresponding to users interacting with and viewing thecollaboration environment and the values of the work unit parameters areorganized in work unit records corresponding to units of work managed,created, and/or assigned within the collaboration environment. Managingthe environment state information may include updating the values of thework unit parameters responsive to user interactions with the units ofwork. The values of the work unit parameters for first unit of work maybe updated responsive to one or more users interacting with the firstunit of work.

The processor(s) may be configured to identify one or more work unitrecords having potentially incorrect status values for a statusparameter. The one or more work unit records having potentiallyincorrect status values may be identified based on the values of thework unit parameters such that a first work unit record having apotentially incorrect first status value is identified based on firstvalues for the work unit parameters associated with the first unit ofwork. The processor(s) may be configured to generate status requestsprompting user input to update the potentially incorrect status valuesfor the one or more work unit records identified. The status requestsmay include a first status request prompting user input from a firstuser associated with the first unit of work to update the potentiallyincorrect first status value. The processor(s) may be configured toeffectuate presentation of the status requests, such that the firststatus request is presented via a client computing platform associatedwith the first user.

In some implementations, a system configured for generating statusrequests for units of work, may include one or more of: one or moreservers, one or more client computing platforms, and/or othercomponents. The one or more servers may be configured to communicatewith one or more client computing platforms according to a client/serverarchitecture and/or other architecture. The one or more servers and/orclient computing platforms may include one or more physical processorsconfigured to execute one or more computer program components. Thecomputer program components may include one or more of an environmentstate component, an identification component, a status requestcomponent, a presentation component, a status update component, anincentive component, and/or other instruction components.

The environment state component may be configured to manage environmentstate information maintaining a collaboration environment. Theenvironment state information may include values of user parameters,values of work unit parameters, and/or values of other parameters. Thevalues of the user parameters may be organized in user recordscorresponding to users interacting with and/or viewing the collaborationenvironment. The values of the work unit parameters may be organized inwork unit records corresponding to units of work managed, created,and/or assigned within the collaboration environment. Managing theenvironment state information may include updating the values of thework unit parameters. The values of the work unit parameters may beupdated responsive to user interactions with the units of work. Forexample, the values of the work unit parameters for first unit of workmay be updated responsive to one or more users interacting with thefirst unit of work. In some implementations, interacting with the firstunit of work may include working on the first unit of work, uploading afile associated with the first unit of work, moving on to another unitof work, not working on the unit of work (e.g., the unit of work beingidle for a given period of time), the user viewing and/or clicking onthe unit of work, and/or other interactions associated with the unit ofwork.

The identification component may be configured to identify one or morework unit records having potentially incorrect status values for astatus parameter. A work unit record may have a potentially incorrectstatus value for a status parameter if, for example, the status of theassociated work unit has not likely been updated and/or likely needs tobe updated. The one or more work unit records having potentiallyincorrect status values may be identified based on the values of thework unit parameters. For example, a first work unit record having apotentially incorrect first status value may be identified based onfirst values for the work unit parameters associated with the first unitof work. In some implementations, the first work unit record may beidentified based on the values for the work unit parameters associatedwith other units of work.

The status request component may be configured to generate statusrequests prompting user input to update the potentially incorrect statusvalues for the one or more work unit records identified. The statusrequests may include, for example, a first status request prompting userinput from a first user associated with the first unit of work to updatethe potentially incorrect first status value. In some implementations,the status requests may be automatically generated responsive to theenvironment state component updating the values of the work unitparameters. In some implementations, a second user may request a statusupdate such that the first status request may be generated responsive toreceiving an update request from a client computing platform associatedwith a second user.

The presentation component may be configured to effectuate presentationof the status requests. For example, the first status request may bepresented within a graphical user interface presented via a clientcomputing platform associated with the first user.

The status update component may be configured to update the status ofthe first unit of work. The status of the first unit of work may beupdated responsive to receiving user input. In some implementations, forexample, the user input may include approval of the first suggestedstatus update, an indication of a status update for the first unit ofwork, and/or other user input. In some implementations, status of thecomponent may be configured to determine a first suggested status updatefor the first status request based on the first values for the work unitparameters associated with the first unit of work. The first suggestedstatus update may be included in the first status request. As such, forexample, presentation component may be configured to effectuatepresentation of the first suggested status update with the first statusrequest.

In some implementations, the incentive component may configured togenerate an incentive offer. The incentive offer may indicate anincentive for the first user based on the first values for the work unitparameters associated with the first unit of work. The presentationcomponent may configured to effectuate presentation of the incentiveoffer to the first user via the first client computing platform. Theincentive component may be configured to provide the incentive to thefirst user responsive to receiving the user input responsive to thefirst status request from the first user. As such, for example, the usermay receive an incentive for updating the status associated with thefirst unit of work and/or responding to the first status request for thefirst unit of work.

These and other features, and characteristics of the present technology,as well as the methods of operation and functions of the relatedelements of structure and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the invention. As usedin the specification and in the claims, the singular form of “a”, “an”,and “the” include plural referents unless the context clearly dictatesotherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system configured for generating status requests forunits of work, in accordance with one or more implementations.

FIG. 2 illustrates an example graphical user interface presentingmultiple status requests, in accordance with one or moreimplementations.

FIG. 3 illustrates an example graphical user interface presenting astatus request, in accordance with one or more implementations.

FIG. 4 illustrates an example graphical user interface presenting astatus request and an incentive offer, in accordance with one or moreimplementations.

FIG. 5 illustrates an example graphical user interface presenting astatus request and an incentive offer, in accordance with one or moreimplementations.

FIG. 6 illustrates a flow chart of a method for generating statusrequests for units of work, in accordance with one or moreimplementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured for generating statusrequests for units of work, in accordance with one or moreimplementations. In some implementations, system 100 may include one ormore servers 102. Server(s) 102 may be configured to communicate withone or more client computing platforms 104 according to a client/serverarchitecture and/or other architectures. Client computing platform(s)104 may be configured to communicate with other client computingplatforms via server(s) 102 and/or according to a peer-to-peerarchitecture and/or other architectures. Users may access system 100 viaclient computing platform(s) 104.

Server(s) 102 may be configured by machine-readable instructions 106.Machine-readable instructions 106 may include one or more instructioncomponents. The instruction components may include computer programcomponents. The instruction components may include one or more of anenvironment state component 108, an identification component 110, astatus request component 112, a presentation component 114, a statusupdate component 116, an incentive component 118, and/or otherinstruction components.

Environment state component 108 may be configured to manage environmentstate information maintaining a collaboration environment. Theenvironment state information may include values of user parameters andvalues of work unit parameters. By way of non-limiting example, thevalues of the user parameters may be organized in user recordscorresponding to users interacting with and viewing the collaborationenvironment. The values of the work unit parameters may be organized inwork unit records corresponding to units of work managed, created,and/or assigned within the collaboration environment. A given work unitmay have one or more assignees and/or team members working on the givenwork unit. Work units may include one or more to-do items, action items,objectives, and/or other units of work one or more users shouldaccomplish and/or plan on accomplishing. Units of work may be created bya given user for the given user and/or created by the given user andassigned to one or more other users. A given unit of work may includeone or more projects, tasks, sub-tasks, and/or other units of workpossibly assigned to and/or associated with one or more users.

The work unit parameters may, by way of non-limiting example, includeone or more of: one or more units of work, one or more user commentparameters (e.g., a creator, a recipient, one or more followers, one ormore other interested parties, content, one or more times, up-votes,other hard-coded responses, etc.), a unit of work name, a unit of workdescription, one or more unit of work dates (e.g., a start date, a duedate, a completion date, and/or other unit of work dates), one or moremembers associated with a unit of work (e.g., an owner, one or moreother project/task members, member access information, and/or other unitof work members and/or member information), a status parameter (e.g., anupdate, a hardcoded status update, a completed/uncomplete/mark complete,a measured status, a progress indication, quantity of sub-work unitsremaining for a given unit of work, completed work units in a givenproject, and/or other status parameter), one or more interactionparameters (e.g., indicating a given unit of work is being worked on/wasworked on, given work unit of work was viewed, a given unit of work wasselected, how long the given unit of work has been idle, a lastinteraction parameter indicating when and what user last interacted withthe given unit of work, users that interacted with the given unit ofwork, and/or otherer interaction parameters indicating sources of theinteractions, context of the interactions, content of the interactionsand/or time for the interactions), one or more file attachments,notification settings, privacy, an associated URL, one or moreinteraction parameters (e.g., sources of the interactions, context ofthe interactions, content of the interactions, time for theinteractions, and/or other interaction parameters), updates, ordering ofunits of work within a given unit of work (e.g., tasks within a project,sub-tasks within a task, etc.,), state of a workspace for a given unitof work (e.g., application state parameters, application status,application interactions, user information, and/or other parametersrelated to the state of the workspace for a unit of work), dependenciesbetween one or more work units, one or more custom fields (e.g.,priority, cost, stage, and/or other custom fields), other work unitparameters for the given work units, and/or other work unit parameters,and/or user parameters for one or more users and/or work units the givenproject is associated with.

The user parameters associated with the users interacting with and/orviewing the collaboration environment may include parameters describingthe users, their actions within the collaboration environment, theirsettings, and/or other user information; and/or metadata associated withthe users, their actions within the environment, their settings, and/orother user information. Individual ones of the users may be associatedwith individual ones of the user records. A user record may definevalues of the user parameters associated with a given user interactingwith and/or viewing the collaboration environment.

The user parameters may, by way of non-limiting example, include one ormore of: a user name, a group parameter, a subset parameter, a useraccount, a user role, a user department, descriptive user content, ato-email, a from-email, a photo, an organization, a workspace, one ormore projects (which may include project parameters defined by one ormore work unit records), one or more items of work (which may includeone or more unit of work parameters defined by one or more unit of workrecords), one or more user comments, one or more teams the user belongsto, one or more of the user display settings (e.g., colors, size,project order, task order, other unit of work order, etc.), one or moreauthorized applications, one or more interaction parameters (e.g.,indicating a user is working on/worked on a given unit of work, a givenuser viewed a given work unit of work, a given user selected a givenunit of work, a timeframe a given user last interacted with and/orworked on a given unit of work, a time period that a given unit of workhas been idle, and/or other interaction parameters), a presenceparameter (e.g., indicating presence and/or interaction level at anenvironment level, unit of work level, project level, task level,application level, etc.), one or more notification settings, one or moreprogress parameters, status information for one or more work units theuser is associated with, one or more statistics related to a given user(e.g., how many units of work the user has completed, how quickly theuser completed the units of work, how quickly the user completes certaintypes of work units, the efficiency of the user, bandwidth of the user,activity level of the user, etc.), application access information (e.g.,username/password for one or more third-party applications), one or morefavorites and/or priorities, workload information, schedule information,historical information, other user parameters for the given user, and/orother user parameters and/or work unit parameters, for one or more workunits the given user is associated with.

The environment state component 108 may be configured to update thevalues of the work unit parameters and/or the user parameters. Managingthe environment state information may include updating the values of thework unit parameters. The values of the work unit parameters may beupdated responsive to user interactions with the units of work.Responsive to a user interacting with a given unit of work, the value ofthe work unit parameters for the given unit of work may be updated. Forexample, the values of the work unit parameters for first unit of workmay be updated responsive to one or more users interacting with thefirst unit of work. Interacting with the first unit of work may includeone or more of working on the first unit of work, uploading a fileassociated with the first unit of work, moving on to another unit ofwork, not working on the unit of work (e.g., the unit of work being idlefor a given period of time), the user viewing and/or clicking on theunit of work, and/or other interactions associated with the unit ofwork.

Identification component 110 may be configured to identify one or morework unit records having potentially incorrect status values for astatus parameter. An incorrect status value for status parameter mayinclude a status value that has not been updated and/or a status valuethat does not accurately reflect the status of the unit of work. The oneor more work unit records having potentially incorrect status values maybe identified based on the values of the work unit parameters. Forexample, the first work unit record is identified as having apotentially incorrect status value. A first work unit record having apotentially incorrect first status value may be identified based onfirst values for the work unit parameters associated with the first unitof work. In some implementations, the first work unit record may beidentified as having a potentially incorrect first status value based onthe values for the work unit parameters associated with other units ofwork.

In some implementations, the values of the work unit parametersindicating that the first work unit record may have a potentiallyincorrect first status value may include a value for a file uploadparameter. When users complete units of work or are close to completingunits of work, they may upload one or more files associated with theunits of work. As such, uploading a file may indicate the status valuefor the status parameter for the unit of work may be incorrect.Responsive to a user uploading a file associated with a given unit ofwork, state component 108 may be configured to update the file uploadparameter for the given unit of work. Identification component 110 maybe configured to identify the work unit record with the newly updatedfile upload parameter as a work unit record having a potentiallyincorrect status value.

In some implementations, the values of the work unit parametersindicating that the first work unit record may have a potentiallyincorrect first status value may include a value for a last interactionparameter corresponding to the first unit of work and/or a second unitof work. The values of a last interaction parameter for multiple unitsof work may be used to identify when a given user moves on to anotherunit of work from a first unit of work possibly indicating the firstunit of work is actually complete. By way of non-limiting example,responsive to the value for a last interaction parameter correspondingto the first unit of work indicating the first user last interacted withthe first unit of work before the value for the him last interactionparameter corresponding to the second unit of work indicates the firstuser last interacted with the second unit of work, identificationcomponent 110 may identify the first work unit record as having apotentially incorrect status value for a status parameter.

In some implementations, the values of the work unit parametersindicating that the first work unit record may have a potentiallyincorrect first status value may include parameter values for one ormore interaction parameters. The interaction parameters may include, forexample a last interaction parameter, an idle parameter (e.g.,indicating a period of time and/or frequency the unit of work is idleand/or not being worked on by a user and/or a given user), aninteraction level parameter (e.g., indicating the type of interactionand/or interaction level with the given unit of work, the frequency ofinteractions, and/or other levels of interaction), and/or otherinteraction parameters.

Status request component 112 may be configured to generate statusrequests prompting user input to update the potentially incorrect statusvalues for the one or more work unit records identified. In someimplementations, the status requests may be automatically generated bystatus request component 112. Status request component 112 mayautomatically generate the status requests for given units of workresponsive to environment state component 108 updating the values of thework unit parameters associated with the given units of work. In someimplementations, status requests may be initiated and/or triggered byanother user (e.g., a manager, a project manager, a supervisor,assigning user, and/or other user). Status requests may includenotifications and/or prompts for user input used to update the statusesthe associated units of work. The user input may include a response tothe status request indicating selection of the correct status for agiven unit of work, approval of a suggested status update, and/or otheruser input.

For example, the status requests may include a first status requestprompting user input from a first user associated with the first unit ofwork to update the potentially incorrect first status value. The firststatus request may be generated automatically and/or responsive toreceiving an update request from a client computing platform associatedwith a second user. The user input may include approval of the firstsuggested status update and/or an indication of a status update for thefirst unit of work. The user input may include selection of a firststatus update for the first unit of work.

Presentation component 114 may be configured to effectuate presentationof the status requests. Status requests may be presented via graphicaluser interface displaying one or more client computing platformsassociated with the users. In some implementations, presentation of thestatus requests may include presentation of one or more suggested statusupdates, options for user input (e.g., options for selection of thecorrect status and/or approval/denial of the correct status for a givenunit of work) and/or other information and/or options. The first statusrequest may be presented via a client computing platform associated withthe first user.

Status update component 116 may be configured to update the status ofone or more units of work responsive to receiving user input in responseto the status requests. For example, status update component 116 may beconfigured to update the first status value for the first unit of workwithin the first work unit record.

In some implementations, status update component 116 may be configuredto determine one or more suggested status updates for a given unit ofwork. The suggested status updates may include proposed status updatesand/or options for a status update from which the user can select. Forexample, status update component 116 may be configured to determine afirst suggested status update for the first status request based on thefirst values for the work unit parameters associated with the first unitof work. The first suggested status update may be included in the firststatus request.

In some implementations, incentive component 118 may be configured togenerate incentive offers for users for updating and/or responding tostatus requests. The incentive offers may be determined based on thevalues for the work unit parameters associated with the given units ofwork. By way of non-limiting example, incentives for status requestsassociated with units of work that have been pending for a long time,involve a lot of users, are associated with higher level users (e.g.,managers, project leads, team leaders, supervisors, etc.), and/or othercharacteristics indicating higher value and/or importance may have morevalue than incentive for status requests associated with units of workthat have only been pending for short period of time, involve a singleuser, are associated with lower level users, and/or othercharacteristics indicating lower value and/or importance. Incentivecomponent 118 may be configured to generate an incentive offerindicating an incentive for the first user based on the first values forthe work unit parameters associated with the first unit of work.

Incentive component 118 may be configured to provide the incentive toone or more users responsive to receiving user input from the one ormore users in response to the given status requests. In someimplementations, incentive component 118 may be configured to providethe incentive to the first user responsive to receiving the user inputin response to the first status request from the first user. Theincentive may include an amount of consideration having some valuewithin and/or external to the collaboration environment.

Returning to presentation component 114, presentation component 114 maybe configured to effectuate presentation of one or more incentive offersfor updating and/or provide a user input in response to the statusupdate requests. As such, for example, presentation component 114 may beconfigured to effectuate presentation of an incentive offer to the firstuser via the first client computing platform.

FIG. 2 illustrates an example graphical user interface presentingmultiple status requests, in accordance with one or moreimplementations. Graphical user interface 200 may be configured toeffectuate presentation of status request 1 204, status request 2 206,and/or status request 3 208. Status request 1 204 may include “yes” and“no” options for user input in response to status request 1 204. Statusrequest 2 206 may include a text box for receiving user input inresponse to status request 2 2-6. Status request 3 208 may include asuggested status update (e.g., marking Project C complete) and requestthe user to improve and/or deny the suggested status update.

FIG. 3 illustrates an example graphical user interface presenting astatus request, in accordance with one or more implementations.Graphical user interface 300 may be configured to effectuatepresentation of status request 4 304 associated with task 2 302. Statusrequest 4 304 may be generated responsive to the values of the work unitparameters associated with task 2 indicating the work unit recordassociated with task 2 may have a potentially incorrect status valuebecause the file upload parameter for tasks 2 was updated. Statusrequest 4 304 may include “yes” and “no” options 306 for user input inresponse to status request 4 304.

FIG. 4 illustrates an example graphical user interface presenting astatus request, in accordance with one or more implementations.Graphical user interface 400 may be configured to effectuatepresentation of status request 5 404 associated with task 4 402. Statusrequest 5 404 may include an incentive offer 405 incentivizing the userto update the task to receive the incentive (e.g., 5 tokens). Responsiveto the user selecting one of the input options 406 (e.g., “completed”,“in progress”, and/or “I need help”), the incentive (e.g., 5 tokens) maybe provided to the user. The status for task 4 402 may be updatedresponsive to and/or based on the user selection of one of the inputoptions (e.g., “completed”, “in progress”, and/or “I need help”).

FIG. 5 illustrates an example graphical user interface presenting astatus request, in accordance with one or more implementations.Graphical user interface 500 may be configured to effectuatepresentation of status request 6 504. Status request 6 504 may includean incentive offer 505 incentivizing the user if task B is complete andthe user selections the update option indicating task B is complete.update the task to receive the incentive (e.g., 5 tokens). Responsive tothe user selecting one of the input options 506 (e.g., “Yes”, “No—It'sin progress”, and/or “No—I need help”), the incentive (e.g., 3 stars)may be provided to the user. The status for task 6 may be updatedresponsive to and/or based on the user selection of one of the inputoptions (e.g., “Yes”, “No—It's in progress”, and/or “No—I need help”).

Returning to FIG. 1 , in some implementations, server(s) 102, clientcomputing platform(s) 104, and/or external resources 124 may beoperatively linked via one or more electronic communication links. Forexample, such electronic communication links may be established, atleast in part, via a network such as the Internet and/or other networks.It will be appreciated that this is not intended to be limiting, andthat the scope of this disclosure includes implementations in whichserver(s) 102, client computing platform(s) 104, and/or externalresources 124 may be operatively linked via some other communicationmedia.

A given client computing platform 104 may include one or more processorsconfigured to execute computer program components. The computer programcomponents may be configured to enable an expert or user associated withthe given client computing platform 104 to interface with system 100and/or external resources 124, and/or provide other functionalityattributed herein to client computing platform(s) 104. By way ofnon-limiting example, the given client computing platform 104 mayinclude one or more of a desktop computer, a laptop computer, a handheldcomputer, a tablet computing platform, a NetBook, a Smartphone, a gamingconsole, and/or other computing platforms.

External resources 124 may include sources of information outside ofsystem 100, external entities participating with system 100, and/orother resources. In some implementations, some or all of thefunctionality attributed herein to external resources 124 may beprovided by resources included in system 100.

Server(s) 102 may include electronic storage 126, one or more processors128, and/or other components. Server(s) 102 may include communicationlines, or ports to enable the exchange of information with a networkand/or other computing platforms. Illustration of server(s) 102 in FIG.1 is not intended to be limiting. Server(s) 102 may include a pluralityof hardware, software, and/or firmware components operating together toprovide the functionality attributed herein to server(s) 102. Forexample, server(s) 102 may be implemented by a cloud of computingplatforms operating together as server(s) 102.

Electronic storage 126 may comprise non-transitory storage media thatelectronically stores information. The electronic storage media ofelectronic storage 126 may include one or both of system storage that isprovided integrally (i.e., substantially non-removable) with server(s)102 and/or removable storage that is removably connectable to server(s)102 via, for example, a port (e.g., a USB port, a firewire port, etc.)or a drive (e.g., a disk drive, etc.). Electronic storage 126 mayinclude one or more of optically readable storage media (e.g., opticaldisks, etc.), magnetically readable storage media (e.g., magnetic tape,magnetic hard drive, floppy drive, etc.), electrical charge-basedstorage media (e.g., EEPROM, RAM, etc.), solid-state storage media(e.g., flash drive, etc.), and/or other electronically readable storagemedia. Electronic storage 126 may include one or more virtual storageresources (e.g., cloud storage, a virtual private network, and/or othervirtual storage resources). Electronic storage 126 may store softwarealgorithms, information determined by processor(s) 128, informationreceived from server(s) 102, information received from client computingplatform(s) 104, and/or other information that enables server(s) 102 tofunction as described herein.

Processor(s) 128 may be configured to provide information processingcapabilities in server(s) 102. As such, processor(s) 128 may include oneor more of a digital processor, an analog processor, a digital circuitdesigned to process information, an analog circuit designed to processinformation, a state machine, and/or other mechanisms for electronicallyprocessing information. Although processor(s) 128 is shown in FIG. 1 asa single entity, this is for illustrative purposes only. In someimplementations, processor(s) 128 may include a plurality of processingunits. These processing units may be physically located within the samedevice, or processor(s) 128 may represent processing functionality of aplurality of devices operating in coordination. Processor(s) 128 may beconfigured to execute components 108, 110, 112, 114, 116, and/or 118and/or other components. Processor(s) 128 may be configured to executecomponents 108, 110, 112, 114, 116, and/or 118 and/or other componentsby software; hardware; firmware; some combination of software, hardware,and/or firmware; and/or other mechanisms for configuring processingcapabilities on processor(s) 128. As used herein, the term “component”may refer to any component or set of components that perform thefunctionality attributed to the component. This may include one or morephysical processors during execution of processor readable instructions,the processor readable instructions, circuitry, hardware, storage media,or any other components.

It should be appreciated that although components 108, 110, 112, 114,116, and/or 118 are illustrated in FIG. 1 as being implemented within asingle processing unit, in implementations in which processor(s) 128includes multiple processing units, one or more of components 108, 110,112, 114, 116, and/or 118 may be implemented remotely from the othercomponents. The description of the functionality provided by thedifferent components 108, 110, 112, 114, 116, and/or 118 described belowis for illustrative purposes, and is not intended to be limiting, as anyof components 108, 110, 112, 114, 116, and/or 118 may provide more orless functionality than is described. For example, one or more ofcomponents 108, 110, 112, 114, 116, and/or 118 may be eliminated, andsome or all of its functionality may be provided by other ones ofcomponents 108, 110, 112, 114, 116, and/or 118. As another example,processor(s) 128 may be configured to execute one or more additionalcomponents that may perform some or all of the functionality attributedbelow to one of components 108, 110, 112, 114, 116, and/or 118.

FIG. 6 illustrates a method 600 for generating status requests for unitsof work, in accordance with one or more implementations. The operationsof method 600 presented below are intended to be illustrative. In someimplementations, method 600 may be accomplished with one or moreadditional operations not described, and/or without one or more of theoperations discussed. Additionally, the order in which the operations ofmethod 600 are illustrated in FIG. 6 and described below is not intendedto be limiting.

In some implementations, method 600 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 600 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 600.

An operation 602 may include managing environment state informationmaintaining a collaboration environment. The environment stateinformation may include values of user parameters and values of workunit parameters. The values of the user parameters may be organized inuser records corresponding to users interacting with and viewing thecollaboration environment and the values of the work unit parameters areorganized in work unit records corresponding to units of work managed,created, and/or assigned within the collaboration environment. Managingthe environment state information may include updating the values of thework unit parameters responsive to user interactions with the units ofwork. The values of the work unit parameters for first unit of work maybe updated responsive to one or more users interacting with the firstunit of work. Operation 602 may be performed by one or more hardwareprocessors configured by machine-readable instructions including acomponent that is the same as or similar to environment state component108, in accordance with one or more implementations.

An operation 604 may include identifying one or more work unit recordshaving potentially incorrect status values for a status parameter. Theone or more work unit records having potentially incorrect status valuesmay be identified based on the values of the work unit parameters suchthat a first work unit record having a potentially incorrect firststatus value is identified based on first values for the work unitparameters associated with the first unit of work. Operation 604 may beperformed by one or more hardware processors configured bymachine-readable instructions including a component that is the same asor similar to identification component 110, in accordance with one ormore implementations.

An operation 606 may include generating status requests prompting userinput to update the potentially incorrect status values for the one ormore work unit records identified. The status requests may include afirst status request prompting user input from a first user associatedwith the first unit of work to update the potentially incorrect firststatus value. Operation 606 may be performed by one or more hardwareprocessors configured by machine-readable instructions including acomponent that is the same as or similar to status request component112, in accordance with one or more implementations.

An operation 608 may include effectuating presentation of the statusrequests, such that the first status request is presented via a clientcomputing platform associated with the first user. Operation 608 may beperformed by one or more hardware processors configured bymachine-readable instructions including a component that is the same asor similar to presentation component 114, in accordance with one or moreimplementations.

Although the present technology has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred implementations, it is to be understoodthat such detail is solely for that purpose and that the technology isnot limited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present technology contemplates that, to theextent possible, one or more features of any implementation can becombined with one or more features of any other implementation.

What is claimed is:
 1. A system configured to generate status requestsfor units of work, the system comprising: one or more hardwareprocessors configured by machine-readable instructions to: manage, by aserver, environment state information maintaining a virtualcollaboration environment, the environment state information includingvalues of user parameters and work unit parameters, wherein the valuesof the user parameters are organized in user records corresponding tousers interacting with and viewing the virtual collaborationenvironment, and the values of the work unit parameters are organized inwork unit records corresponding to units of work managed, created,and/or assigned within the virtual collaboration environment, whereinindividual units of work are individual action items individual ones ofthe users are to accomplish, wherein the users interact with and viewthe virtual collaboration environment via remotely located clientcomputing platforms communicating with the server over an Internetconnection, wherein managing the environment state information includesupdating the values of the work unit parameters responsive to userinteractions with the units of work, such that the values of the workunit parameters for a first unit of work are updated responsive to oneor more of the users interacting with the first unit of work; establishthe Internet connection between the remotely located client computingplatforms and the server; identify, by the server, one or more of thework unit records having potentially incorrect status values for astatus parameter for the individual units of work, status valuescharacterizing status of the individual units of work, wherein the oneor more of the work unit records having the potentially incorrect statusvalues are identified based on the values of the work unit parameterssuch that a first work unit record having a potentially incorrect firststatus value is identified based on first values for the work unitparameters associated with the first unit of work; generate, by theserver, status requests prompting user input to update the potentiallyincorrect status values for the one or more of the work unit records,the status requests including a first status request prompting the userinput from a first user associated with the first unit of work to updatethe potentially incorrect first status value; effectuate communicationof information from the server to the remotely located client computingplatforms over the Internet connection so that the remotely locatedclient computing platforms present a user interface of the virtualcollaboration environment including the status requests, the statusrequests in the user interface including user-selectable input elementsthrough which the users provide the user input to update the potentiallyincorrect status values, such that the first status request is presentedvia a first remotely located client computing platform associated withthe first user, the first status request including a firstuser-selectable input element and a second user-selectable input elementthrough which the first user provides the user input to update thepotentially incorrect first status value; obtain, at the server, userinput information conveying the user input into the user interface atthe remotely located client computing platforms b the users; and update,at the server, the potentially incorrect status values based on the userinput information conveying the user input, such that responsive to theuser input of the first user including selection of the firstuser-selectable input element, update the potentially incorrect firststatus value to a first updated value, and responsive to the user inputof the first user including selection of the second user-selectableinput element, update the potentially incorrect first status value to asecond updated value.
 2. The system of claim 1, wherein interacting withthe first unit of work includes one or more of working on the first unitof work, and/or uploading a file associated with the first unit of work.3. The system of claim 1, wherein the first work unit record isidentified based on the values for the work unit parameters associatedwith other units of work.
 4. The system of claim 1, wherein generatingthe status requests includes automatically generating the statusrequests responsive to updating the values of the work unit parameters.5. The system of claim 1, wherein the first status request is generatedresponsive to receiving an update request from a second client computingplatform associated with a second user.
 6. The system of claim 1,wherein the one or more hardware processors are further configured bythe machine-readable instructions to: determine a first suggested statusupdate for the first status request based on the first values for thework unit parameters associated with the first unit of work, wherein thefirst user-selectable input element conveys the first suggested statusupdate.
 7. The system of claim 6, wherein the user input of the firstuser including the selection of the first user-selectable input elementconveys approval of the first suggested status update and/or anindication of a status update for the first unit of work.
 8. The systemof claim 1, wherein the one or more hardware processors are furtherconfigured by the machine-readable instructions to generate an incentiveoffer indicating an incentive for the first user based on the firstvalues for the work unit parameters associated with the first unit ofwork.
 9. The system of claim 8, wherein the one or more hardwareprocessors are further configured by the machine-readable instructionsto: effectuate presentation of the incentive offer to the first user viathe first remotely located client computing platform; provide theincentive to the first user responsive to receiving the user putresponsive to the first status request from the first user.
 10. Thesystem of claim 1, wherein the values of the work unit parametersindicating that the one or more of the work unit records have thepotentially incorrect status values include the values of a file uploadparameter and/or a last interaction parameter.
 11. The system of claim10, wherein the values of the work unit parameters indicating that thefirst work unit record has the potentially incorrect first status valueinclude a value for the last interaction parameter corresponding to thefirst unit of work and/or a second unit of work, such that responsive tothe value for the last interaction parameter corresponding to the firstunit of work indicating the first user last interacted with the firstunit of work before the value for the last interaction parametercorresponding to the second unit of work indicates the first user lastinteracted with the second unit of work, the first work unit record isidentified as having the potentially incorrect first status value.
 12. Acomputer-implemented method to generate status requests for units ofwork, the method comprising: managing, by a server, environment stateinformation maintaining a virtual collaboration environment, theenvironment state information including values of user parameters andvalues of work unit parameters, wherein the values of the userparameters are organized in user records corresponding to usersinteracting with and viewing the virtual collaboration environment, andthe values of the work unit parameters are organized in work unitrecords corresponding to units of work managed, created, and/or assignedwithin the virtual collaboration environment, wherein individual unitsof work are individual action items individual ones of the users are toaccomplish, wherein the users interact with and view the virtualcollaboration environment via remotely located client computingplatforms communicating with the server over an Internet connection,wherein the managing the environment state information includes updatingthe values of the work unit parameters responsive to user interactionswith the units of work, including updating the values of the work unitparameters for a first unit of work responsive to one or more of theusers interacting with the first unit of work; establishing the Internetconnection between the remotely located client computing platforms andthe server; identifying, by the server, one or more of the work unitrecords having potentially incorrect status values for a statusparameter for the individual units of work, status values characterizingstatus of the individual units of work, wherein the one or more of thework unit records having the potentially incorrect status values areidentified based on the values of the work unit parameters, includingidentifying a first work unit record as having a potentially incorrectfirst status value based on first values for the work unit parametersassociated with the first unit of work; generating, by the server,status requests prompting user input to update the potentially incorrectstatus values for the one or more of the work unit records identified,the status requests including a first status request prompting userinput from a first user associated with the first unit of work to updatethe potentially incorrect first status value; effectuating communicationof information from the server to the remotely located client computingplatforms over the Internet connection so that the remotely locatedclient computing platforms present a user interface of the virtualcollaboration environment including the status requests, the statusrequests in the user interface including user-selectable input elementsthrough which the users provide the user input to update the potentiallyincorrect status values, including presenting the first status requestvia a first remotely located client computing platform associated withthe first user, the first status request including a firstuser-selectable input element and a second user-selectable input elementthrough which the first user provides the user input to update thepotentially incorrect first status value; obtaining, at the server, userinput information conveying the user input into the user interface atthe remotely located client computing platforms by the users; andupdating, at the server, the potentially incorrect status values basedon the user input information conveying the user input, includingresponsive to the user input of the first user including selection ofthe first user-selectable input element, updating the potentiallyincorrect first status value to a first updated value, and responsive tothe user input of the first user including selection of the seconduser-selectable input element, updating the potentially incorrect firststatus value to a second updated value.
 13. The method of claim 12,wherein interacting with the first unit of work includes one or more ofworking on the first unit of work, and/or uploading a file associatedwith the first unit of work.
 14. The method of claim 12, wherein thefirst work unit record is identified based on the values for the workunit parameters associated with other units of work.
 15. The method ofclaim 12, wherein the generating the status requests includesautomatically generating the status requests responsive to updating thevalues of the work unit parameters.
 16. The method of claim 12, whereinthe first status request is generated responsive to receiving an updaterequest from a second client computing platform associated with a seconduser.
 17. The method of claim 12, further comprising: determining afirst suggested status update for the first status request based on thefirst values for the work unit parameters associated with the first unitof work, wherein the first user-selectable input element conveys thefirst suggested status update.
 18. The method of claim 17, wherein theuser input of the first user including the selection of the firstuser-selectable input element conveys approval of the first suggestedstatus update and/or an indication of a status update for the first unitof work.
 19. The method of claim 12, further comprising generating anincentive offer indicating an incentive for the first user based on thefirst values for the work unit parameters associated with the first unitof work.
 20. The method of claim 19, further comprising: effectuatingpresentation of the incentive offer to the first user via the firstremotely located client computing platform; and providing the incentiveto the first user responsive to receiving the user input responsive tothe first status request from the first user.
 21. The method of claim12, wherein the values of the work unit parameters indicating that theone or more of the work unit records have the potentially incorrectstatus values include the values of a file upload parameter and/or alast interaction parameter.
 22. The method of claim 21, wherein thevalues of the work unit parameters indicating that the first work unitrecord has the potentially incorrect first status value include a valuefor the last interaction parameter corresponding to the first unit ofwork and/or a second unit of work, such that responsive to the value forthe last interaction parameter corresponding to the first unit of workindicating the first user last interacted with the first unit of workbefore the value for the last interaction parameter corresponding to thesecond unit of work indicates the first user last interacted with thesecond unit of work, the first work unit record is identified as havingthe potentially incorrect first status value.